Because we want to add allow_consumer_teams later to also give the option to users to filter which teams can consume their events, I think it is better to collapse all these options under one parameter access_control of the Asset object.

This PR update the documentation, implementation is available here: #66954

Documentation preview

Assets

Multi-team

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.